Consent on Profile #7211
Merged
Consent on Profile #7211
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for segment-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for segment-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
pwseg
approved these changes
May 14, 2025
| Events without the consent object will continue to flow to destinations without consent enforcement. | ||
| Events without the consent object will continue to flow to destinations without consent enforcement. | ||
|
|
||
| Segment events without a context or consent object or that have an empty context or consent object do not impact [consent preferences on the Profile](/docs/privacy/consent-management/consent-in-unify) and these events will flow to all destinations. |
There was a problem hiding this comment.
Suggested change
| Segment events without a context or consent object or that have an empty context or consent object do not impact [consent preferences on the Profile](/docs/privacy/consent-management/consent-in-unify) and these events will flow to all destinations. | |
| Segment events without a context or consent object or that have an empty context or consent object do not impact [consent preferences on the Profile](/docs/privacy/consent-management/consent-in-unify) and these events will flow to all destinations. |
There's a lot of branching with these or clauses, any way we could simplify this sentence? Maybe something like "Events that don't include a context object, a consent object, or that include them but leave them empty, don’t affect profile-level consent preferences and will be sent to all destinations."
Or maybe "Segment events that are missing a context or consent object (or include them without any values) will still flow to all destinations and won't update consent preferences on the Profile."
forstisabella
commented
May 14, 2025
src/privacy/consent-management/consent-in-segment-connections.md
Outdated
Show resolved
Hide resolved
pwseg
approved these changes
May 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Update Consent in Unify page to be Consent on Profile, add net-new content
Merge timing
TBD - requires PM approval
Related issues (optional)
#5738
DOC-792